Overview

When you attempt to disable a cube from SAS OLAP Cube Studio or SAS Data Integration Studio, you might see a message that is similar to the following:

ERROR: The application could not log on to the server "server.name.com:####". No server is available at that port on that machine.

Typically, this problem occurs if you are using a load-balanced SAS OLAP Server and some of the servers in the cluster are not started.

To work around this issue, use PROC OLAPOPERATE to disable cubes.

SAS^® 9.4 and later

Beginning with SAS 9.4, you can use the DISABLE CUBE statement available in PROC OLAPOPERATE to disable one or more cubes across all load-balanced OLAP servers. You need to reference only the primary OLAP Server port for the PORT connection option of the CONNECT command.

For example, suppose that your load-balanced OLAP Server runs on ports 5451 and 5452. You can disable a cube in both load-balanced servers by specifying port 5421 as shown in the following PROC OLAPOPERATE code:

PROC OLAPOPERATE;
   CONNECT host="myserver.com" Port=5451 userid="user" password="pword";
   DISABLE CUBE "cubeName";
QUIT;

SAS 9.3 and earlier

In SAS 9.3 and earlier, you must include a CONNECT command with PORT connection option for each load-balanced OLAP Server. For example, if your load-balanced OLAP Server runs on ports 5451 and 5452, you must submit a CONNECT command and DISABLE CUBE statement for each OLAP Server in the load-balanced cluster, as shown in the following sample code:

PROC OLAPOPERATE;
   CONNECT host="myserver.com" Port=5451 userid="user" password="pword";
   DISABLE CUBE "cubeName";
   DISCONNECT;
   CONNECT host="myserver.com" Port=5452 userid="user" password="pword";
   DISABLE CUBE "cubeName";
QUIT; 

For more information about the OLAPOPERATE procedure, see the SAS OLAP Server User's Guide for your release of SAS.

Operating System and Release Information

A fix for this issue for SAS Management Console 9.4_M3 is available at:

A fix for this issue for Data Integration Studio 4.901 is available at:

A fix for this issue for SAS Middle Tier 9.4_M3 is available at:

A fix for this issue for SAS OLAP Cube Studio 4.4_M3 is available at: